System and method for communication with a tracking device

ABSTRACT

A system and method for providing communication with a tracking device are disclosed. An example tracking device includes a location detector, a communication device, memory, a processor, and a configuration routine. The location detector is operative to determine locations of the tracking device. The communication device is operative to communicate with a remote system. The memory stores data and code, the data including location data determined by the location detector and configuration data. The processor is operative to execute the code to impart functionality to the tracking device. The functionality of the tracking device depends at least in part on the configuration data. The configuration routine is operative to modify the configuration data responsive to communications from the remote system. Thus, functional access to the tracking device is provided to the remote system.

RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.14/313,339, filed Jun. 24, 2014 by at least one common inventor, whichis a divisional of U.S. patent application Ser. No. 13/443,180 (now U.S.Pat. No. 8,760,286), filed Apr. 10, 2012 by at least one commoninventor, which is a continuation of U.S. patent application Ser. No.12/322,941 (now U.S. Pat. No. 8,154,401), filed Feb. 9, 2009 by at leastone common inventor, which claims the benefit of U.S. Provisional PatentApplication No. 61/065,116 filed Feb. 8, 2008 by at least one commoninventor, all of which are incorporated herein by reference in theirrespective entireties.

BACKGROUND

Technical Field

This invention relates generally to a system and method for monitoringlocation, and more specifically to a system and method for enablingcommunication with a tracking device.

Background Art

Currently, systems exist for tracking the location of persons and/orproperty. Generally, such systems include a tracking device thattransmits the location of the tracking device to a central station,which may then take some action based on the location data.

Known systems have generally been very limited with respect to thecommunication capabilities between the tracking device and the centralstation. For example, communications from a tracking device to a centralstation have typically been limited to the transmission of a deviceidentifier in combination with location data and, in some cases, adistress signal.

Perhaps, the limited communication between tracking devices and centralstations has evolved due to the disadvantages of prior art trackingsystems. For example, in personal tracking devices power consumption isa serious concern, because the devices power storage capacity is alimiting factor with respect to the amount of communication that cantake place. Another concern is the cost of network access (e.g., mobilephone air time).

What is needed is a system and method for providing enhancedcommunication with tracking devices. What is also needed is a system andmethod for providing enhanced communication with tracking devices, whileminimizing power consumption. What is also needed is a system and methodfor providing enhanced communication with tracking devices, whileminimizing network air time.

SUMMARY

A system and method for providing communication with a tracking deviceis disclosed. The inventor has discovered that several advantages areprovided by the communication system and methods disclosed herein. Theseadvantages include the efficient use of network access time and theconservation of tracking device power. Additional advantages includeenhanced efficiency and flexibility in the communication of locationdata from tracking devices. Yet another advantage is that functionalaccess (e.g., setting and/or resetting of functions, parameters, etc.)to the tracking device is provided to the central station. These andother advantages will be apparent to those skilled in the art in view ofthe following disclosure.

In a disclosed example, a tracking device includes a location detector,a communication device, memory, a processor, and a configurationroutine. The location detector (e.g., a Global Positioning Satellitereceiver) is operative to determine locations of the tracking device.The communication device (e.g., a cell phone modem) is operative tocommunicate with a remote system (e.g., a central station, subscriberserver, etc.). The memory stores data and code, the data includinglocation data determined by the location detector and configurationdata. The processor is operative to execute the code to impartfunctionality to the tracking device. The functionality of the trackingdevice depends at least in part on the configuration data. Theconfiguration routine is operative to modify the configuration dataresponsive to a communication from the remote system. Thus, functionalaccess to the tracking device is provided to the remote system.

The tracking device can be configured and reconfigured in many ways. Inone example, the configuration data modifiable responsive to thecommunication from the remote system at least partially determines aninterval for communicating the location data to the remote system. Inanother example, the configuration data modifiable responsive to thecommunication from the remote system at least partially determines aninterval for buffering the location data when the communication deviceis unable to communicate the location data to the remote system (e.g.,out of communication range). The interval for buffering the locationdata can be, for example and without limitation, a time interval (e.g.,every 30 minutes) or a distance interval (e.g., whenever the trackingdevice moves 50 yards). In yet another example, the configuration datamodifiable responsive to the communication from the remote system atleast partially determines a power state of the location detector. Inyet another example, the configuration data modifiable responsive to thecommunication from the remote system at least partially determines amonitored condition with respect to the location of the tracking device(e.g., a “geofence”). For example and without limitation, the monitoredcondition can be a geographical area (e.g., circular or polygonal,etc.), a velocity, a distance, a time/distance relationship (e.g., atime the tracking device remains stationary), or any combination ofthese. In yet another example, the configuration data modifiableresponsive to the communication from the remote system at leastpartially determines a threshold distance between one of the locationsand subsequent ones of the locations for storing the subsequent ones ofthe locations (e.g., only buffer location data if the tracking devicehas moved at least the threshold distance). As even yet another example,the configuration data modifiable responsive to the communication fromthe remote system at least partially determines an interval forcommunicating diagnostic information from the tracking device to theremote system.

The example tracking device also includes a data transfer routineoperative to communicate operational data between the tracking deviceand the remote system. In one example, the tracking device includes abattery and the data transfer routine responsive to a request from theserver is operative to communicate data indicative of the status of thebattery to the remote system. In another example, the data transferroutine responsive to a request from the server is operative tocommunicate data indicative of a radio signal strength to the remotesystem. In yet another example, the data transfer routine responsive toa request from the server is operative to communicate data indicative ofa status of the location detector to the remote system. In yet anotherexample, the data transfer routine responsive to a status of a monitoredlocation condition (e.g., a geofence definition) is operative tocommunicate data indicative of a violation or satisfaction of thelocation condition to the remote system. As yet another example, thedata transfer routine responsive to a request from the server isoperative to communicate diagnostic data to the remote system.

Another feature of the example tracking device is that when thecommunication device is unable to establish a connection with the remotesystem, the location data is accumulated in the memory. Then, when thecommunication device is able to establish a connection with the remoteserver, the data transfer routine communicates the accumulated data tothe remote system.

An example method for communicating with a tracking device is alsodisclosed. The method includes communicating with the tracking devicevia a wireless network and providing configuration data to the trackingdevice via the wireless network. The configuration data causes thetracking device to operate according to a first configuration. Themethod further includes receiving processed data from the trackingdevice. The processed data is generated by the tracking device in thefirst configuration. The method further includes providing newconfiguration data to the tracking device via the wireless network. Thenew configuration data changes the first configuration of the trackingdevice to a different configuration. The method further includesreceiving additional processed data from the tracking device. Theadditional processed data is generated by the tracking device in thedifferent configuration.

In the example method, the configuration data at least partiallydetermines a location data reporting interval. In another examplemethod, the configuration data at least partially determines a locationdata buffering interval. In yet another example method, theconfiguration data at least partially determines a power state of thetracking device. In yet another example method, the configuration dataat least partially determines a location based condition that ifviolated or satisfied causes an indication of the violation orsatisfaction of the location based condition to be communicated from thetracking device to the remote system. In yet another example method, theconfiguration data at least partially determines a diagnostic reportinginterval. In yet another example method, the configuration data at leastpartially determines a distance threshold for buffering location data.In yet another example method, the processed data includes dataindicative of a battery status of the tracking device. In yet anotherexample method, the processed data includes data indicative of a radiosignal strength determined by the tracking device. In yet anotherexample method, the processed data includes data generated by adiagnostic routine of the tracking device.

Many other detailed examples are disclosed in the communication protocolspecification set forth below.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described with reference to the followingdrawings, wherein like reference numbers denote substantially similarelements:

FIG. 1 is a block diagram of a tracking system;

FIG. 2 is a block diagram of a server of the tracking system of FIG. 1;

FIG. 3 is a block diagram of a subscriber system of the tracking systemof FIG. 1;

FIG. 4 is a block diagram of a tracking device of the tracking system ofFIG. 1; and

FIG. 5 is a flow chart summarizing an example method of communicatingwith the tracking device of FIG. 1 and FIG. 4.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of a system 100 for tracking and/or monitoringone or more tracking devices 102(1-m). System 100 includes one or moreservers 104(1-m), a subscriber profile database 106, a vendorinformation database 108, a public database cache 110, and trackinginterface 112, all intercommunicating via an internal network 114.System 100 communicates with remote components including one or morevendors 116(1-n), one or more subscribers 118(1-p), and one or morepublic databases 120(1-q), all via an internetwork 122 (e.g., theInternet). A firewall 124 provides a measure of security for internalnetwork 114 against threats via internetwork 122.

Servers 104 host services for subscribers 118 and/or other authorizedusers that facilitate the tracking and/or monitoring of the location oftracking devices 102. Subscriber profile database 106 stores informationassociated with particular subscribers 118 and/or other users of system100. Vendor information database 108 stores information associated withvendors 116 that provide goods and or services that can be madeavailable to subscribers 118 and/or other users of system 100 based oninformation from subscriber profile database 106 and/or location datareceived from tracking devices 102. Public database cache 110 providestemporary storage for data retrieved from public databases 120. Trackinginterface 112 transmits (via wireless communication) data and commandsto tracking devices 102 and receives data (e.g., location data, sensorreadings, distress signal, etc.) from tracking devices 102. Vendors 116offer goods and services that may be offered to subscribers and otherusers of system 100 as described above. In addition, informationassociated with vendors (e.g., type of business) can be used to helpdefine boundaries used to monitor tracking devices 102. Similarly,public databases 120 provide information (e.g., sex offender registries,etc.) that can be used as criteria for defining boundaries.

Subscribers 118 are the primary users of system 100 and interact withservers 104 to define tracking criteria and to obtain information andalerts regarding the tracking of associated tracking devices 102. Inthis example, the primary users are referred to as subscribers, becauseit is expected that users will be willing to pay for the right to usesystem 100. However, it should be understood that system 100 is notlimited to a subscription type business model. For example, access tosystem 100 could be provided to users on a free basis, relying on someother business model to raise revenue.

In addition communication between tracking devices 102 and servers 104,the communication methods described herein can be used to provide directcommunication between tracking devices 102 and subscribers 118 via acommunication link (e.g., mobile phone network), which is not shown inFIG. 1. Similarly, the communication methods described herein can beused to provide direct communication between tracking devices 102 (e.g.,GPS enabled cell phone to GPS enabled cell phone). In that case trackingdevices 102 can function as both a tracking device and a subscribersystem.

FIG. 2 is a block diagram of a server 102 of tracking system 100. Server102 includes non-volatile data storage 202, one or more processing units204, memory 206, user I/O devices 208, and a network interface 210.Nonvolatile data storage 202 stores data and code that is retained evenwhen server 104 is powered down. Memory 206 stores data and code thatwhen processed by processing unit(s) 204 imparts functionality to server104. User input/output devices 208 (e.g., keyboard, mouse, monitor,etc.) provide a means of interaction between server 104 and a localhuman user. Network interface 210 provides a communication link to othercomponents on internal network 114 and internetwork 122.

For the sake of clear explanation data and code are shown in memory 206as functional blocks. It should be understood, however, that the variousfunctions of server 104 need not be run in any particular location ofmemory 206 and may grouped in any useful manner. For example, theseveral application program interfaces (APIs) shown could be groupedinto a single API.

Memory 206 includes an operating system 214, public database API 216,subscriber API 218, processing queues 220, vendor API 222, control andcoordination routines 224, application programs 226, and a trackingdevice communication protocol 228. Operating system 214 provides lowlevel control of server 104 and provides a platform on top of which theother modules can operate. Application programs 226 are tracking serviceprograms that receive and process location and/or sensor data fromtracking devices 102, process the received data, communicate withsubscribers 118, read and/or update subscriber profile database 106,search remote data sources, and so on. Public database API 216, vendorAPI 222, and subscriber API 218 provide a means of communication betweenapplication programs 226 and public databases 120, vendors 116, andsubscribers 118, respectively. Control and coordination module 224provides overall control and coordination of the tracking servicesprovided by server 104. Processing queues 220 provide temporary storagefor tracking data that is being processed.

Tracking device communication protocol 228 defines a protocol forcommunicating with tracking device 102. In this particular embodiment,this communication occurs via network 114, tracking interface 112, andthe wireless connection with tracking devices 102. It is sometimes,therefore, referred to as the over-the-air protocol. The definitions andfunctionality of an example tracking device communication protocol 228is fully described below.

FIG. 3 is a block diagram of a subscriber system 118 of tracking system100. Subscriber system 118 includes non-volatile data storage 302, oneor more processing units 304, memory 306, user I/O devices 308, and anetwork interface 310, all intercommunicating via a bus 312. Memory 306includes operating system 314, application programs 316, subscriber API318, and tracking device communication protocol 320. Applicationprograms 316 provide various tracking based services (e.g., set uptracking account, associate particular tracking devices 102 with useraccount, receive and/or display real time and/or historical locationinformation associated with particular tracking devices 102, and so on).Subscriber API 318 (in conjunction with subscriber API 218 of server 104shown in FIG. 2) facilitates communication between application programs316 of subscriber system 118 and application programs 226 of server 104(FIG. 2).

Tracking device communication protocol 320 is similar to tracking devicecommunication protocol 228 of server 104, except that tracking devicecommunication protocol 320 resides on a subscriber system 118.Therefore, tracking device communication protocol 320 facilitates directcommunication between subscriber system 118 and tracking device 102 viaa separate communication link (not shown), such as a mobile telephonenetwork.

FIG. 4 is a block diagram of a tracking device 102 of tracking system100. Tracking device server 102 includes non-volatile data storage 402,one or more processing unit(s) 404, memory 406, location detector (e.g.,GPS receiver) 408 with optional sensors (e.g., temperature sensor,motion sensor, etc.), and a wireless communication device 410, allintercommunicating via a bus 412. Memory 406 includes an operatingsystem 414, application programs 416, a tracking API 418, location data420, tracking device communication protocol 422, and sensor data 424.Application programs 416 facilitate the processing of location data 420and/or sensor data 424, provide alerts and/or updates to server 104(FIG. 1), facilitate updates to existing routines or the addition of newroutines, and provide any other specified functionality for trackingdevice 102. For example, application programs 416 can be updated orreplaced by server 104 via tracking interface 112. Tracking APIfacilitates communication between application programs 416 andapplication programs 226 of server 104, for example, to communicatelocation data from tracking device 102 to server 104. Sensor data 424and location data 420 can be accessed by application programs 416 asneeded. Data indicative of the velocity of tracking device 102 can becharacterized as either sensor data or location data. Tracking devicecommunication protocol 422 is similar to tracking device communicationprotocol 228, except that tracking device protocol 422 operates on thedevice side of the communication link.

The following is a detailed description of a particular example of atracking device communication protocol.

1. Gradient Fields

1.1 Overview

Many of the fields within the structures in this document use indexvalues to pass a value measured by or stored at the device.

When a data field is defined as a gradient, the firmware will calculatean index value as the number of increments from a defined base value.This value, an integer, will be placed within the structure fortransmission.index=(measurement−base)/increment

When the server receives the index value, that actual measured value iscalculated by first retrieving the pre-defined values for base,increment, and unit of measure from a table lookup. These values arestored based on Device Type and Firmware Version, and are applieduniformly for all devices sharing these characteristics.

Once the server has retrieved the conversion values, the actualmeasurement value is calculated asmeasurement=base+(index*increment)

The server will can then store the calculated result as a high-precisionvalue in the database. System presentation layers can convert thesevalues to the localized measurement system for display, using the unitof measure field as a helper.

1.2 Field List with Suggested Metrics

The following table lists the structure fields defined as gradientfields. All gradient fields are defined as integer values.

The suggested base and increment are suggested values only. Thedeveloper must decide the actual base and increment to meet therequirements for range and granularity imposed by the specificimplementation.

Field Type Incre- Unit of Range Definition Data Type Base ment Measure(Rounded) RSSI Byte −113 2 dBm −113 to 397 dBm BATTERY Unsigned 0 1 mV 0to 65.5 volts Short ALTITUDE Unsigned −4000 1 Decimeter −400 to 6,153Short meters/ −1312 to 20,188 feet SPEED Unsigned 0 1 Dekameters 0 to6,553 Short meters per hour/0 to 407 miles per hour BEARING Unsigned 0 11/100^(ths) of a 360 degrees Short degree DISTANCE Unsigned 0 1Hectometers 0 to 6,553 Short kilometers/0 to 4,072 miles DOP Byte 0 0.2Absolute 0 to 50.8 VDOP Byte 0 0.2 Absolute 0 to 50.8 HDOP Byte 0 0.2Absolute 0 to 50.8 GPSSNR Byte 0 1 dB 0 to 255 dB2. Data Types

The following data types are referenced in this document.

2.1 Primitives

Name Byte Length Comment Byte 1 No type checking Short Integer 2 Integervalues from −32,768 to 32,767. Little endian. Unsigned Short 2 Integervalues from 0 to 65,535. Little endian. Integer 4 Integer values from−2147483648 to 2147483647. Little endian. Unsigned Integer 4 Integervalues from 0 to 4,294,967,296. Little endian. Float 4 Asingle-precision 32-bit IEEE 754 floating point value.2.2 Defined Types

Name Data Type Length Comment DATETIME Byte Array 6 YMDHMS CRC32 Integer4 Result of CRC-32 hash LATITUDE Float 4 LONGITUDE Float 4 DATETIMEUnsigned Integer 4 RSSI Byte 1 Gradient field containing the datatransceiver Received Signal Strength Indication BATLEVEL Unsigned Short2 Gradient field containing battery condition. ALTITUDE Unsigned Short 2Gradient field containing an altitude value. SPEED Unsigned Short 2Gradient field containing a speed or velocity value. BEARING UnsignedShort 2 Gradient field containing a compass bearing or course directionvalue. DISTANCE Unsigned Short 2 Gradient field containing a lineardistance value.3. Constants

The following constant values are referenced in this document.

3.1 Transport Structure IDs

See section 5 Structure Summary.

3.2 Device Types

Name Value Comment DT_HERMES 0x01 Use for Hermes hardware specificationdevices. DT_PPC 0x02 Use for Windows Pocket PC devices.3.3 GPS Fix States

Name Value Comment GPS_NOFIX 0x01 GPS is powered on but could notestablish a fix. GPS_SEARCHING 0x02 GPS is establishing a fix.GPS_LOCONLY 0x03 GPS fix two dimensional without altitude. GPS_LOCALT0x04 GPS has a full three dimension fix with altitude. GPS_POWEROFF 0x05GPS is powered off.3.4 GPS Power States

Name Value Comment GPS_POWERDOWN 0x01 Power down the GPS. GPS_POWERUP0x02 Power up the GPS and attempt to obtain a fix. GPS_POWERDOWNUNTIL0x03 Power down until the wake up time.3.5 Interactivity Modes

Name Value Comment IMODE_HIGN 0x01 High Interactivity mode. IMODE_LOW0x02 Low Interactivity mode.3.6 Geofence Types

Name Value Comment GFT_INCLUSION 0x01 GFT_EXCLUSION 0x02 GFT_BOTH 0x03GFT_POLYGON 0x04 GPT_CIRCULAR 0x05 GFT_VELOCITY 0x06 GFT_STATIONARY 0x07GFT_MOVEMENT 0x083.7 NACK Types

Name Value Comment NACK_UNKNOWN 0x01 NACK_NOT_SUPPORTED 0x02NACK_FAIILED_CRC 0x03 NACK_INVALID_LENGTH 0x044. Structure Summary

Utility structures are not included in the summary.

Orientation Manifest Mobile Host to Protocol Usage Structure Name TypeValue to host Mobile UDP RHTTP DHTTP TCP SMS UDP_ENVELOPE Transport n.a.✓ ✓ ✓ RHTTP_ENVELOPE Transport n.a. ✓ ✓ ✓ DHTTP_ENVELOPE Transport n.a.✓ ✓ ✓ TCP_ENVELOPE Transport n.a. ✓ ✓ ✓ SMS_ENVELOPE Transport n.a. ✓ ✓✓ GET_DEVICE_ID Request 0x0101 ✓ ✓ ✓ ✓ ✓ ✓ GET_CURRENT_LOCATION Request0x0102 ✓ ✓ ✓ ✓ ✓ ✓ GET_BATTERY_STATUS Request 0x0103 ✓ ✓ ✓ ✓ ✓ ✓GET_RSSI Request 0x0104 ✓ ✓ ✓ ✓ ✓ ✓ GET_GPS_STATUS Request 0x0105 ✓ ✓ ✓✓ ✓ ✓ GET_GEOFENCE_HANDLE Request 0x0106 ✓ ✓ ✓ ✓ ✓ ✓ GET_GEOFENCESRequest 0x0107 ✓ ✓ ✓ ✓ ✓ ✓ ✓ GET_CUSTOM_PARAM Request 0x0108 ✓ ✓ ✓ ✓ ✓ ✓GET_DIAGNOSTIC Request 0x0109 ✓ ✓ ✓ ✓ ✓ ✓ GET_SYSTEMTIME Request 0x010A✓ ✓ ✓ ✓ ✓ ✓ SET_REPORTING_INTERVAL Request 0x0201 ✓ ✓ ✓ ✓ ✓ ✓SET_GPS_POWERSTATE Request 0x0202 ✓ ✓ ✓ ✓ ✓ ✓ SET_BUFFERING_INTERVALRequest 0x0203 ✓ ✓ ✓ ✓ ✓ ✓ SET_START_BUFFER Request 0x0204 ✓ ✓ ✓ ✓ ✓ ✓SET_END_BUFFER Request 0x0205 ✓ ✓ ✓ ✓ ✓ ✓ SET_HEARTBEAT_PARAMETERSRequest 0x0206 ✓ ✓ SET_INTERACTIVITY_MODE Request 0x0207 ✓ ✓ ✓SET_CIRCULAR_GEOFENCE Request 0x0208 ✓ ✓ ✓ ✓ ✓ ✓ SET_POLYGON_GEOFENCERequest 0x0209 ✓ ✓ ✓ ✓ ✓ ✓ SET_VELOCITY_GEOFENCE Request 0x020A ✓ ✓ ✓ ✓✓ ✓ SET_STATIONARY_GEOFENCE Request 0x020B ✓ ✓ ✓ ✓ ✓ ✓SET_DELETE_GEOFENCE Request 0x020C ✓ ✓ ✓ ✓ ✓ ✓ SET_CUSTOM_PARAM Request0x020D ✓ ✓ ✓ ✓ ✓ ✓ SET_REPORTING_GRANULARITY Request 0x020E ✓ ✓ ✓ ✓ ✓ ✓SET_MOVEMENT_GEOFENCE Request 0x020F ✓ ✓ ✓ ✓ ✓ ✓ SET_DIAGNOSTIC_INTERVALRequest 0x0210 ✓ ✓ ✓ ✓ ✓ ✓ SET_DEBUG_LEVEL Request 0x0211 ✓ ✓ ✓ ✓ ✓ ✓PUT_CURRENT_LOCATION Response 0x0301 ✓ ✓ ✓ ✓ ✓ ✓ PUT_BATTERY_STATUSResponse 0x0302 ✓ ✓ ✓ ✓ ✓ ✓ PUT_RSSI Response 0x0303 ✓ ✓ ✓ ✓ ✓ ✓PUT_GPS_STATUS Response 0x0304 ✓ ✓ ✓ ✓ ✓ ✓ PUT_GEOFENCE_HANDLE Response0x0305 ✓ ✓ ✓ ✓ ✓ ✓ PUT_GEOFENCE Response 0x0306 ✓ ✓ ✓ ✓ ✓ ✓PUT_CUSTOM_PARAM Response 0x0307 ✓ ✓ ✓ ✓ ✓ ✓ PUT_LOCATION Response0x0308 ✓ ✓ ✓ ✓ ✓ ✓ PUT_GEOFENCE_VIOLATION Response 0x0309 ✓ ✓ ✓ ✓ ✓ ✓PUT_DEVICE_ID Response 0x030A ✓ ✓ ✓ ✓ ✓ ✓ PUT_LOCATION_ARRAY Response0x030B ✓ ✓ ✓ ✓ ✓ ✓ PUT_DIAGNOSTIC Response 0x030C ✓ ✓ ✓ ✓ ✓ ✓PUT_SYSTEMTIME Response 0x030D ✓ ✓ ✓ ✓ ✓ ✓ PUT_DEBUG_MESSAGE Response0x030E ✓ ✓ ✓ ✓ ✓ ✓ ACK_MOBILE Acknow. 0x0401 ✓ ✓ ✓ ✓ ✓ ✓ ACK_HOSTAcknow. 0x0402 ✓ ✓ ✓ ✓ ✓ ✓ NACK_MOBILE Acknow. 0x0403 ✓ ✓ ✓ ✓ ✓ ✓NACK_HOST Acknow. 0x0404 ✓ ✓ ✓ ✓ ✓ ✓5. Utility Structures5.1 Structure POSITION

POSITION defines a geographic position.

Member Name Data Type Bytes Comments Latitude LATITUDE 4 LongitudeLONGITUDE 4 TOTAL 85.2 Structure CORNER

CORNER defines a corner of a polygon geofence.

Member Name Data Type Bytes Comments Sequence Number Byte 1 The numberof the corner in clockwise sequence. Position POSITION 8 The geographicposition of the corner. TOTAL 95.3 Structure LOCATE

LOCATE defines complete information about the device location in amoment in time.

Member Name Data Type Bytes Comments Position POSITION 8 Geographicposition of the device. Fix Time DATETIME 6 Byte array [YMDHMS] Fix TypeByte 1 GPS Fix Type Speed SPEED 2 Speed gradient value Bearing BEARING 2Bearing gradient value Linear Motion DISTANCE 2 Linear distance gradientvalue Altitude ALTITUDE 2 Altitude gradient value TOTAL 226. Transport Envelope Structures

Transport Envelopes contain transport-specific information necessary toensure reliable deliver of information between host and mobileapplications. Each transport has a specific transport envelope that allrequest and response transaction structures are encapsulated within.

6.1 Structure UDP_ENVELOPE

The UDP Transport Envelope is use to encase all UDP transport requestand response structures.

Member Name Data Type Bytes Comments Checksum CRC32 4 Checksum of therequest/response structure using the CRC-32 algorithm. SeqNo Byte 1Sequence Number. Increment with each NEW transmission. No carry. Usesame SeqNo for retransmissions. Payload Size Unsigned Short 2SizeOf(Payload) Payload Array of Byte N Contains the request or responsestructure being transported. TOTAL N + 86.2 Structure RHTTP_ENVELOPE

The Reverse HTTP Transport Envelope is use to encase all Reverse HTTPtransport request and response structures.

6.2.1 Structure RHTTP_ENVELOPE

Member Name Data Type Bytes Comments Timeout Unsigned Short 2 The numberof seconds the client will maintain the open HTTP request waiting for aresponse from the host. Checksum CRC32 4 Checksum of therequest/response structure using the CRC-32 algorithm. Payload SizeUnsigned Short 2 SizeOf(Payload) Payload Array of Byte N Contains therequest or response structure being transported. TOTAL N + 86.3 Structure DHTTP_ENVELOPE

The Direct HTTP Transport Envelope is use to encase all Direct HTTPtransport request and response structures.

Member Name Data Type Bytes Comments Checksum CRC32 4 Checksum of therequest/response structure using the CRC-32 algorithm. Payload SizeUnsigned Short 2 SizeOf(Payload) Payload Array of Byte N Contains therequest or response structure being transported. TOTAL N + 66.4 Structure TCP_ENVELOPE

The TCP Transport Envelope is use to encase all TCP transport requestand response structures.

Member Name Data Type Bytes Comments Checksum CRC32 4 Checksum of therequest/response structure using the CRC-32 algorithm. Payload SizeUnsigned Short 2 SizeOf(Payload) Payload Array of byte N Contains therequest or response structure being transported. TOTAL N + 66.5 Structure SMS_ENVELOPE

The SMS Transport Envelope is use to encase all SMS transport requestand response structures.

Member Name Data Type Bytes Comments Checksum CRC32 4 Checksum of therequest/response structure using the CRC-32 algorithm. Payload SizeUnsigned Short 2 SizeOf(Payload) Payload Array of Byte N Contains therequest or response structure being transported. TOTAL N + 87. GET Request Structures

GET request structures can be used to initiate both host-to-mobile andmobile-to-host application-layer transactions. These requests contain arequest for data, which is typically acknowledged by a corresponding PUTresponse structure containing the requested data.

7.1 Structure GET_DEVICE_ID

GET_DEVICE_ID is used by the device during first time initialization toobtain a unique device identifier from the GTX host platform. Thisunique device identifier is the primary method by which the device datais organized within the GTX platform. Most subsequent requests require avalid device identified as a structure member.

7.1.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓7.1.2 Request Orientation

Mobile-to-host Host-to-mobile ✓7.1.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device SN Array[1 . . . 15 Contains a string 15] of byte representationof device IMEI (GSM) or MEID (CDMA). If the IMEI or ESN can not beobtained from the device, it is acceptable to submit the telephonenumber. This field is padded with nulls. (0x00). Firmware Float 4Contains the firmware Version revision of the device expressed as amajor version integer minor version fraction. Device Type Byte 1Contains the device type constant. TOTAL 227.1.4 Expected Response

A properly formatted GET_DEVICE_ID request structure will be respondedto from the host with a PUT_DEVICE_ID response structure.

7.2 Structure GET_CURRENT_LOCATION

GET_CURRENT_LOCATION is used by the host to request the most recentlocation coordinates from the mobile.

7.2.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓7.2.2 Request Orientation

Mobile-to-host Host-to-mobile ✓7.2.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 TOTAL27.2.4 Expected Response

A properly formatted GET_CURRENT_LOCATION request structure will beresponded to from the mobile with a PUT_CURRENT_LOCATION responsestructure.

7.3 Structure GET_BATTERY_STATUS

GET_BATTERY_STATUS is used by the host to request the current batterycondition from the mobile.

7.3.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓7.3.2 Request Orientation

Mobile-to-host Host-to-mobile ✓7.3.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 TOTAL27.3.4 Expected Response

A properly formatted GET_BATTERY_STATUS request structure will beresponded to from the mobile with a PUT_BATTERY_STATUS responsestructure.

7.4 Structure GET_RSSI

GET_RSSI is used by the host to request the current radio signalstrength condition from the mobile.

The mobile actually replies with and index value from 0 to 255 thathashes the actual measured signal quality.

The host calculates the actual signal quality value by referencing in atable containing domain parameters for this device type. The serverstores the BASE value, the INCREMENT, an override value for transmittingthe signal quality is UNKNOWN, and UNIT of measure field used forformatting the value for display.

If the server received value is equal to UNKNOWN, an undefined orunknown signal quality is calculated, otherwise the server calculatesthe signal quality value for by multiplying the received index byINCREMENT and adding the product to BASE.

7.4.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓7.4.2 Request Orientation

Mobile-to-host Host-to-mobile ✓7.4.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 TOTAL27.4.4 Expected Response

A properly formatted GET_RSSI request structure will be responded tofrom the mobile with a PUT_RSSI response structure.

7.5 Structure GET_GPS_STATUS

GET_GPS_STATUS is used by the host to request the current condition ofthe GPS receiver from the mobile.

7.5.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓7.5.2 Request Orientation

Mobile-to-host Host-to-mobile ✓7.5.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 TOTAL27.5.4 Expected Response

A properly formatted GET_GPS_STATUS request structure will be respondedto from the mobile with a PUT_GPS_STATUS response structure.

7.6 Structure GET_GEOFENCE_HANDLE

GET_GEOFENCE_HANDLE is used by the host to request the handle for thenext available geofence parameters storage area.

7.6.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓7.6.2 Request Orientation

Mobile-to-host Host-to-mobile ✓7.6.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 TypeByte 1 Geofence type TOTAL 37.6.4 Expected Response

The device must respond with a PUT_GEOFENCE_HANDLE transactioncontaining the handle to the available storage location, or a NACK ifstorage is full or the geofence type is unsupported.

7.7 Structure GET_GEOFENCES

GET_GEOFENCES is used by the host to request an iteration of thegeofence parameter data currently stored on the device.

7.7.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓7.7.2 Request Orientation

Mobile-to-host Host-to-mobile ✓ ✓7.7.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 TOTAL27.7.4 Expected Response

The device must respond iteratively with one PUT_GEOFENCE message foreach set of geofence data currently stored. The device should NACK ifnot geofences are stored.

7.8 Structure GET_CUSTOM_PARAM

GET_CUSTOM_PARAM is used to query a custom parameter value, such as acarrier-specific connection parameter. The parameter name to query isspecified in a variable length field. Up to 255 characters may be sentusing this structure, however the response will be formatted as a stringin NAME=VALUE format up to 255 bytes in length.

7.8.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓7.8.2 Request Orientation

Mobile-to-host Host-to-mobile ✓7.8.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2BufferLen Byte 1 SizeOf(Buffer) Buffer Array[1 . . . N NAME part ofBufferLen] of Byte NAME = VALUE parameter format. TOTAL N + 37.8.4 Expected Response

A properly formatted GET_CUSTOM_PARAM should be acknowledged with aPUT_CUSTOM_PARAM structure containing the response in NAME=VALUE format.

7.9 Structure GET_DIAGNOSTIC

GET_DIAGNOSTIC is used to make a one-time request for a completediagnostic payload. Use SET_DIAGNOSTIC_INTERVAL to establish periodicreporting of the diagnostics by the device.

7.9.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓7.9.2 Request Orientation

Mobile-to-host Host-to-mobile ✓7.9.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 TOTAL27.9.4 Expected Response

A properly formatted GET_DIAGNOSTIC should be acknowledged with aPUT_DIAGNOSTIC structure.

7.10 Structure GET_SYSTEMTIME

GET_SYSTEMTIME is used to request the current UTC date and time at thehost.

7.10.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓7.10.2 Request Orientation

Mobile-to-host Host-to-mobile ✓7.10.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 TOTAL27.10.4 Expected Response

A properly formatted GET_SYSTEMTIME should be acknowledged with aPUT_SYSTEMTIME structure.

8. SET Request Structures

SET request structures are used to initiate both host-to-mobile andmobile-to-host application-layer transactions. These structures containa command to alter the system running state or modify an internalparameters or values. SET requests are typically confirmed with ageneric acknowledgement.

8.1 Structure SET_REPORTING_INTERVAL

SET_REPORTING_INTERVAL is used by the host to set the autonomouslocation report interval. When the reporting interval is set to anon-zero value, the mobile report automatically transmits asynchronousPUT_LOCATION structures according to the set interval.

8.1.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.1.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.1.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 MinInterval Unsigned Short 2 Minimum reporting interval in seconds. Set toZero to turn off autonomous reporting. Reports will be sent NOT MOREoften then this, regardless of the distance trigger. Max IntervalUnsigned Short 2 Maximum reporting interval in seconds. Set to Zero toturn off autonomous reporting. Reports will be sent AT LEAST this often,if the distance trigger is not met. Linear Distance DISTANCE 2 Distancereporting Trigger trigger gradient. Reports will be sent when thisaccumulated distance is traveled. TOTAL 88.1.4 Expected Response

A properly formatted SET_REPORTING_INTERVAL should be acknowledged witha ACK_MOBILE structure with the Acknowledgement field set toSET_REPORTING_INTERVAL.

8.2 Structure SET_GPS_POWERSTATE

SET_GPS_POWERSTATE is used by the host to set the power state of the GPSreceiver.

8.2.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.2.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.2.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned 2 Short NewPower Byte 1 One of the GPS Power State State Constants. Wakeup DATETIME6 If the power state is being set to GPS_POWERDOWNUNTIL, this fieldspecifies that date and time to power back up. TOTAL 98.2.4 Expected Response

A properly formatted SET_GPS_POWERSTATE should be acknowledged with aACK_MOBILE structure with the Acknowledgement field set toSET_GPS_POWERSTATE.

8.3 Structure SET_BUFFERING_INTERVAL

SET_BUFFERING_INTERVAL is used by the host to set the local locationbuffering interval. The buffering interval controls how frequentlylocation records will be stored in the device memory in the event of atemporary out-of-coverage condition. The buffer is implemented as acircular queue. When the allocated storage for the buffer is used, newentries overwrite the oldest entry in the buffer.

8.3.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.3.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.3.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 MinInterval Unsigned Short 2 Minimum reporting interval in seconds. Set toZero to turn off autonomous reporting. Locates will be buffered NOT MOREoften then this, regardless of the distance trigger. Max IntervalUnsigned Short 2 Maximum reporting interval in seconds. Set to Zero toturn off autonomous reporting. Locates will be buffered AT LEAST thisoften, if the distance trigger is not met. Linear Distance DISTANCE 2Distance reporting Trigger trigger gradient. Locates will be bufferedwhen this accumulated distance is traveled. TOTAL 88.3.4 Expected Response

A properly formatted SET_BUFFERING_INTERVAL should be acknowledged withan ACK_MOBILE structure with the Acknowledgement field set toSET_BUFFERING_INTERVAL.

8.4 Structure SET_START_BUFFER

SET_START_BUFFER starts a dump of the current location buffer from themobile to the host. When the mobile receives a request to start sendingbuffered data, it will begin traversing the circular queue starting withthe oldest record, sending each record to the host using a PUT_LOCATIONstructure. Reporting stops when a SET_END_BUFFER request is received, orwhen the newest buffered data has been transmitted.

8.4.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.4.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.4.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 TOTAL38.4.4 Expected Response

A properly formatted SET_START_BUFFER structure should be acknowledgedwith a PUT_LOCATION structure containing the oldest record in thebuffer.

8.5 Structure SET_END_BUFFER

SET_END_BUFFER stops a dump of the location buffer from the mobile.

8.5.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.5.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.5.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 TOTAL28.5.4 Expected Response

A properly formatted SET_END_BUFFER should be acknowledged with aACK_MOBILE structure with the Acknowledgement field set toSET_END_BUFFER.

8.6 Structure SET_HEARTBEAT_PARAMETERS

SET_HEARTBEAT_PARAMETERS is used to set the starting parameters for theHTTP session timeout for the Reverse HTTP Transport.

8.6.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓8.6.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.6.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Starting Interval Unsigned Short 2 Starting interval in seconds. StepInterval Unsigned Short 2 The amount to add or subtract from the timeoutafter a successful session or a timeout. Interval Limit Unsigned Short 2The longest timeout interval the system will seek to, in seconds. TOTAL88.6.4 Expected Response

A properly formatted SET_HEARTBEAT_INTERVAL should be acknowledged withan ACK_MOBILE structure with the Acknowledgement field set toSET_HEARTBEAT_INTERVAL.

8.7 Structure SET_INTERACTIVITY_MODE

SET_INTERACTIVITY_MODE is used to set the toggle between HighInteractivity and Low Interactive Mode for Reverse HTTP Transportdevices.

When this command is sent via SMS, it still applies to the devicesReverse HTTP Transport mode. In this case, it is used as an out-of-bandsignal to switch to High Interactivity mode and force immediate ReverseHTTP session establishment.

8.7.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓8.7.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.7.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Interactivity Mode Byte 1 One of the Interactivity Mode constants.Polling Rate Unsigned Short 2 For Low Interactivity mode, this sets thepolling rate in seconds. TOTAL 88.7.4 Expected Response

A properly formatted SET_INTERACTIVITY_MODE should be acknowledged withan ACK_MOBILE structure with the Acknowledgement field set toSET_INTERACTIVITY_MODE.

8.8 Structure SET_CIRCULAR_GEOFENCE

SET_CIRCULAR_GEOFENCE is used to create a circular area which the deviceto generate alerts if the area in entered or exited.

8.8.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.8.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.8.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Handle Byte 1 Center POSITION 8 Radius DISTANCE 2 Distance gradientvalue Type Byte 1 GFT_INCLUSION GFT_EXCLUSION GFT_BOTH TOTAL 168.8.4 Expected Response

ACK is the device accepts the geofence, NACK if the handle is invalid orthe geofence type is unsupported.

8.9 Structure SET_POLYGON_GEOFENCE

SET_CIRCULAR_GEOFENCE is used to create a rectangular area which thedevice will generate alerts if the area in entered or exited.

8.9.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.9.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.9.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Handle Byte 1 Corner Count Byte 1 Corners Array[1 . . . N * 8     CornerCount] of CORNER Type Byte 1 GFT_INCLUSION GFT_EXCLUSION GFT_BOTH TOTALN * 8 + 58.9.4 Expected Response

ACK is the device accepts the geofence, NACK if the handle is invalid orthe geofence type is unsupported.

8.10 Structure SET_VELOCITY_GEOFENCE

SET_CIRCULAR_GEOFENCE is used to create a threshold speed which thedevice will generate alerts if the threshold is exceeded.

8.10.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.10.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.10.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Handle Byte 1 Speed SPEED 2 Speed gradient value TOTAL 118.10.4 Expected Response

ACK is the device accepts the geofence, NACK if the handle is invalid orthe geofence type is unsupported.

8.11 Structure SET_STATIONARY_GEOFENCE

SET_STATIONARY_GEOFENCE is used to create a threshold period of timewhich the device will generate alerts if it is stationary for a periodof time greater than the threshold.

8.11.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.11.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.11.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Handle Byte 1 Trigger Speed SPEED 2 Speed gradient value Time at RestDATETIME 6 TOTAL 138.11.4 Expected Response

ACK is the device accepts the geofence, NACK if the handle is invalid orthe geofence type is unsupported.

8.12 Structure SET_DELETE_GEOFENCE

SET_DELETE_GEOFENCE is used to delete the parameters associated with aparticular geofence and suppress alerting based on those parameters.

8.12.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.12.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.12.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Handle Byte 1 TOTAL 38.12.4 Expected Response

ACK is the geofence could be deleted, NACK if the handle is invalid.

8.13 Structure SET_CUSTOM_PARAM

SET_CUSTOM_PARAM is used to set a custom parameter, such as acarrier-specific connection parameter. The parameter is specified in avariable length field in NAME=VALUE format. Up to 255 characters may besent using this structure.

8.13.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.13.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.13.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2BufferLen Byte 1 SizeOf(Buffer) Buffer Array[1 . . . BufferLen] of NParameter in Byte NAME = VALUE format. TOTAL N + 38.13.4 Expected Response

A properly formatted SET_CUSTOM_PARAM should be acknowledged with anACK_MOBILE structure with the Acknowledgement field set toSET_CUSTOM_PARAM.

8.14 Structure SET_REPORTING_GRANULARITY

SET_REPORTING_GRANULARITY is used to set the threshold distance betweeninternal location samples. When a reporting granularity value is set,the device will not accumulate inter-sample distances below the setdistance. This is designed to dampen phantom location “drift” generatedby a stationary device.

8.14.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.14.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.14.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Distance DISTANCE 2 Distance gradient value TOTAL 48.14.4 Expected Response

A properly formatted SET_REPORTING_GRANULARITY should be acknowledgedwith a ACK_MOBILE structure with the Acknowledgement field set toSET_REPORTING_GRANULARITY.

8.15 Structure SET_MOVEMENT_GEOFENCE

SET_MOVEMENT_GEOFENCE is used to create a threshold distance which thedevice to generate alerts if that distance is traveled. This isdifferent than setting reporting based on distance because when amovement geofence is set, the device will report PUT_GEOFENCE_VIOLATIONwhen the distance has been traveled.

8.15.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.15.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.15.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Handle Byte 1 Trigger Distance DISTANCE 2 Distance gradient value TOTAL118.15.4 Expected Response

ACK is the device accepts the geofence, NACK if the handle is invalid orthe geofence type is unsupported.

8.16 Structure SET_DIAGNOSTIC_INTERVAL

SET_DIAGNOSTIC_INTERVAL is used by the host to set the request periodicdiagnostic payload reporting. When the reporting interval is set to anon-zero value, the mobile automatically transmits asynchronousPUT_DIAGNOSTIC structures according to the set interval.

8.16.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.16.2 Request Orientation

Mobile-to-host Host-to-mobile ✓8.16.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 MinInterval Unsigned Short 2 Minimum reporting interval in seconds. Set toZero to turn off autonomous reporting. Reports will be sent NOT MOREoften then this, regardless of the distance trigger. Max IntervalUnsigned Short 2 Maximum reporting interval in seconds. Set to Zero toturn off autonomous reporting. Reports will be sent AT LEAST this often,if the distance trigger is not met. Linear Distance DISTANCE 2 Distancereporting Trigger trigger gradient. Reports will be sent when thisaccumulated distance is traveled. TOTAL 88.16.4 Expected Response

A properly formatted SET_DIAGNOSTIC_INTERVAL should be acknowledged witha ACK_MOBILE structure with the Acknowledgement field set toSET_DIAGNOSTIC_INTERVAL.

8.17 Structure SET_DEBUG_LEVEL

SET_DEBUG_LEVEL is used by the host to set the debug reporting level forthe device. Debug level 0 turns off reporting. Other levels are firmwaredefined. Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓8.17.1 Request Orientation

Mobile-to-host Host-to-mobile ✓8.17.2 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 DebugLevel Byte 1 TOTAL 38.17.3 Expected Response

A properly formatted SET_DEBUG_LEVEL should be acknowledged with aACK_MOBILE structure with the Acknowledgement field set toSET_DEBUG_LEVEL.

9. PUT Response Structures

PUT Request structures are used to acknowledge host-to-mobile andmobile-to-host application-layer transactions. These structurestypically contain a response to a GET request.

PUT requests may also be used to asynchronously deliver eventnotifications. When delivering an asynchronous notification, they may beconfirmed with a generic acknowledgement.

9.1 Structure PUT_CURRENT_LOCATION

PUT_CURRENT_LOCATION is used to respond to and acknowledge aGET_CURRENT_LOCATION request.

9.1.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.1.2 Orientation

Mobile-to-host Host-to-mobile ✓9.1.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned Integer 4 Device ID returned in the PUT_DEVICE_IDresponse. Location LOCATE 22 TOTAL 289.2 Structure PUT_BATTERY_STATUS

PUT_BATTERY_STATUS is used to respond to and acknowledge aGET_BATTERY_STATUS request.

9.2.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.2.2 Orientation

Mobile-to-host Host-to-mobile ✓9.2.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned Integer 4 Device ID returned in the PUT_DEVICE_IDresponse. Battery Level BATLEVEL 4 TOTAL 109.3 Structure PUT_RSSI

PUT_RSSI is used to respond to and acknowledge a GET_RSSI request.

The mobile actually replies with and index value from 0 to 255 thathashes the actual measured signal quality.

The host calculates the actual signal quality value by referencing in atable containing domain parameters for this device type. The serverstores the BASE value, the INCREMENT, an override value for transmittingthe signal quality is UNKNOWN, and UNIT of measure field used forformatting the value for display.

If the server receives value is equal to UNKNOWN, an undefined orunknown signal quality is calculated, otherwise the server calculatesthe signal quality value for by multiplying the received index byINCREMENT and adding the product to BASE.

9.3.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.3.2 Orientation

Mobile-to-host Host-to-mobile ✓9.3.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned 4 Device ID returned in the Integer PUT_DEVICE_IDresponse. Radio Signal Strength RSSI 1 TOTAL 79.4 Structure PUT_GPS_STATUS

PUT_GPS_STATUS is used to respond to and acknowledge a GET_GPS_STATUSrequest.

9.4.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.4.2 Orientation

Mobile-to-host Host-to-mobile ✓9.4.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned Integer 4 Device ID returned in the PUT_DEVICE_IDresponse. Fix Type Byte 1 One of the GPS Fix State constants. SatellitesByte 1 Number of satellites in view of the receiver. DOP Byte 1Gradient; Dilution of Precision from the GPS, if available. VDOP Byte 1Gradient; Vertical Dilution of Precision from the GPS, if available.HDOP Byte 1 Gradient; Horizontal Dilution of Precision from the GPS, ifavailable. Accuracy Byte 1 Accuracy in meters. 255 is used for anythinggreater than 254. TOTAL 119.5 Structure PUT_GEOFENCE_HANDLE

The device responds to a GET_GEOFENCE_HANDLE message withPUT_GEOFENCE_HANDLE. After retrieving the handle, the host can set ageofence using the supplied handle.

9.5.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.5.2 Request Orientation

Mobile-to-host Host-to-mobile ✓9.5.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned Integer 4 Device ID returned in the PUT_DEVICE_IDresponse. Handle Byte 1 TOTAL 79.5.4 Expected Response

The host should transmit a desired geofence message type using thesupplied handle.

9.6 Structure PUT_GEOFENCE

PUT_GEOFENSE is used by the device to transmit the parameters of aparticular geofence. PUT_GEFENCE could used in response to a require fora specific geofence's parameters, or PUT_GEOFENCE could be transmittediteratively for each stored geofence in response to GET_GEOFENSES.

9.6.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.6.2 Request Orientation

Mobile-to-host Host-to-mobile ✓9.6.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned Integer 4 Handle Byte 1 Type Byte 1 Geofence typeRadius Unsigned Integer 4 Corner Count Byte 1 Corners Array[1 . . .Corner Count] N * 9 of CORNER TOTAL N * 9 + 139.7 Structure PUT_CUSTOM_PARAM

PUT_CUSTOM_PARAM is used to respond to a GET_CUSTOM_PARAM structure withthe value of a custom parameter, such as a carrier-specific connectionparameter. The response is formatted in a variable length field inNAME=VALUE format. Up to 255 characters may be sent using thisstructure.

9.7.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.7.2 Request Orientation

Mobile-to-host Host-to-mobile ✓9.7.3 Structure Definition

Member Name Data Type Bytes Comments Structure Unsigned Short 2 IDDevice ID Unsigned Integer 4 Device ID returned in the PUT_DEVICE_IDresponse. BufferLen Byte 1 SizeOf(Buffer) Buffer Array[1 . . .BufferLen] of N Parameter in Byte NAME = VALUE format. TOTAL N + 79.8 Structure PUT_LOCATION

PUT_LOCATION is used to send an unacknowledged coordinate fix from themobile to the host. This coordinate fix may be initiated by a requestfrom the host to begin autonomous interval reporting, or to streambuffered location data in response to a request from the host to dumpthe buffer, or may be initiated by the device after aback-in-cellular-coverage condition.

9.8.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.8.2 Orientation

Mobile-to-host Host-to-mobile ✓9.8.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned Integer 4 Device ID returned in the PUT_DEVICE_IDresponse Location LOCATE 22 TOTAL 289.9 Structure PUT_GEOFENCE_VIOLATION

PUT_GEOFENCE_VIOLATION is used to signal that a geofence boundary hasbeen crossed or a threshold has been exceeded.

9.9.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.9.2 Orientation

Mobile-to-host Host-to-mobile ✓9.9.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned Integer 4 Device ID returned in the PUT_DEVICE_IDresponse. Handle Byte 1 Geofence Handle Location LOCATE 22 TOTAL 299.10 Structure PUT_DEVICE_ID

PUT_DEVICE_ID is send by the host in response to a GET_DEVICE_ID requeststructure.

9.10.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.10.2 Request Orientation

Mobile-to-host Host-to-mobile ✓9.10.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned Integer 4 TOTAL 69.11 Structure PUT_LOCATION_ARRAY

PUT_LOCATION_ARRAY is used to send multiple coordinate fixes from themobile to the host. This may be initiated by a request from the host tobegin to stream buffered location data in response to a request from thehost to dump the buffer, or may be initiated by the device after aback-in-cellular-coverage condition.

PUT_LOCATION_ARRAY should be used whenever more than one buffered locaterecord is being set to the host. The maximum number of locates that canbe passed in the array is 255, but implementation limitations such asmaximum transport payload may significantly limit this number. It is thedeveloper's responsibility to insure that a structure small enough to besupported by the transport layer is created.

9.11.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.11.2 Orientation

Mobile-to-host Host-to-mobile ✓9.11.3 Structure Definition

Member Name Data Type Bytes Comments Structure Unsigned Short 2 IDDevice ID Unsigned Integer 4 Device ID returned in the PUT_DEVICE_IDresponse Array Size Byte 1 Number of LOCATE elements in the arrayLocations Array[1 . . . Array N * 22 Size] of LOCATE TOTAL 7 + (N * 22)9.11.4 Expected Response

Because of the relatively large amount of data carried in aPUT_LOCATION_ARRAY structure, it should be acknowledged with an ACK_HOSTstructure with the Acknowledgement field set to PUT_LOCATION_ARRAY.

9.12 Structure PUT_DIAGNOSTIC

PUT_DIAGNOSTIC is used to respond to and acknowledge a GET_DIAGNOSTICrequest and to send periodic diagnostic payloads if requested bySET_DIAGNOSTIC_INTERVAL.

9.12.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.12.2 Orientation

Mobile-to-host Host-to-mobile ✓9.12.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned Integer 4 Device ID returned in the PUT_DEVICE_IDresponse. Location LOCATION 20 GPSSNR Byte 1 GPS Signal to noise ratioin dB Battery Level BATLEVEL 2 Satellites Byte 1 Number of satellites inview of the receiver. Accuracy Byte 1 Accuracy in meters. 255 is usedfor anything greater than 254. DOP Byte 1 Gradient; Dilution ofPrecision from the GPS, if available. VDOP Byte 1 Gradient; VerticalDilution of Precision from the GPS, if available. HDOP Byte 1 Gradient;Horizontal Dilution of Precision from the GPS, if available. NetworkStatus Byte 1 TOTAL 289.13 Structure PUT_SYSTEMTIME

PUT_SYSTEMTIME is used to respond to and acknowledge a GET_SYSTEMTIMErequest and to send the current UTC date and time at the host.

9.13.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.13.2 Orientation

Mobile-to-host Host-to-mobile ✓9.13.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2System Time DATETIME 6 UTC time at the host. TOTAL 89.14 Structure PUT_DEBUG_MESSAGE

PUT_DEBUG_MESSAGE is used to send debugging messages from the device tothe server. This is a firmware defined implementation.

9.14.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓9.14.2 Orientation

Mobile-to-host Host-to-mobile ✓9.14.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2 DebugMessage Binary Var Variable length field. TOTAL Var10. Acknowledgements

Acknowledgements are generic positive and negative confirmations ofrequests and notifications. They are also used to carry “no operation”signaling for some transport models.

10.1 Structure ACK_MOBILE

ACK_MOBILE is a generic acknowledgement for requests from the host thatdo not have a specific response structure.

ACK_MOBILE is also used as a special purpose structure to open an HTTPtransmission channel from the mobile to the host. The mobile will keepthe HTTP session open for the period of time defined in the Timeoutvalue in the Reverse HTTP Transport Envelope. If the host desired tosend an application-layer request to the mobile, it creates a properlyformatted request structure within a Reverse HTTP Transport Envelope,BINHEX encodes the entire payload, transmits the payload through theopen socket, and closes the socket.

10.1.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓10.1.2 Orientation

Mobile-to-host Host-to-mobile ✓10.1.3 Structure Definition

Member Name Data Type Byte Comments Structure ID Unsigned Short 2 DeviceID Unsigned Integer 4 Device ID returned in the PUT_DEVICE_ID responseAcknowledgement Unsigned Short 2 The Structure ID of the lasttransmission to acknowledge. Baggage Unsigned Short 2 Additionalacknowledgement information. TOTAL 1010.2 Structure ACK_HOST

ACK_HOST is a generic acknowledgement for requests from the mobile thatdo not have a specific response structure.

ACK_HOST is also a special purpose structure used to close an HTTPtransmission channel from the when the timeout period is about to expireand the host does not need to submit a command to the mobile. ACK_HOSTsimple tells the mobile that the data session is still active.Typically, the mobile will reestablish a new HTTP session with the host,submitting an ACK_MOBILE structure. In Reverse HTTP High Interactivitymode, this reestablishment will occur immediately, and in Reverse HTTPLow Interactivity mode, the client will wait a defined amount of timebefore re-polling the host for a command.

10.2.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓10.2.2 Orientation

Mobile-to-host Host-to-mobile ✓10.2.3 Structure Definition

Member Name Data Type Byte Comments Structure ID Unsigned Short 2Acknowledgement Unsigned Short 2 The Structure ID of the lasttransmission to acknowledge. Baggage Unsigned Short 2 Additionalacknowledgement information. TOTAL 610.3 Structure NACK_MOBILE

NACK_MOBILE is used to negatively acknowledge a request structurereceived by the mobile device. NACK should only be used if the envelopefails checksum verification or if an unsupported request is made by thehost.

10.3.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓10.3.2 Orientation

Mobile-to-host Host-to-mobile ✓10.3.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Short 2Device ID Unsigned 4 Device ID returned in the Integer PUT_DEVICE_IDresponse. Do not NACK an invalid response to GET_DEVICE_ID. Resend theGET_DEVICE_ID request. Acknowledgement Unsigned Short 2 The Structure IDof the transmission to that generated the error. Baggage Unsigned Short2 Additional acknowledgement information. Type Byte 1 NACK Type constantTOTAL 1110.4 Structure NACK_HOST

NACK_HOST is used to negatively acknowledge a request structure receivedby the host. NACK_HOST should only be used if the envelope failschecksum verification or if an unsupported request is made by themobile.

10.4.1 Protocol Usage

UDP Reverse HTTP Direct HTTP TCP SMS ✓ ✓ ✓ ✓ ✓10.4.2 Orientation

Mobile-to-host Host-to-mobile ✓10.4.3 Structure Definition

Member Name Data Type Bytes Comments Structure ID Unsigned Integer 2Acknowledgement Unsigned Short 2 The Structure ID of the transmission tothat generated the error. Baggage Unsigned Short 2 Additionalacknowledgement information. Type Byte 1 NACK Type constant TOTAL 711. UDP Transport Use Cases

UDP Transactions consist of a properly formatted request structureplaced inside a properly formatted UDP transport envelope structure andsent to the GTX platform host address.

11.1 Mobile Client First-Time Initialization or Cold-Start

Mobile-to-host Host-to-mobile GET_DEVICE_ID PUT_DEVICE_ID11.2 Host Request Location

Host-to-mobile Mobile-to-host GET_CURRENT_LOCATION PUT_CURRENT_LOCATION11.3 Start or Stop Interval Location Reporting

Host-to-mobile Mobile-to-host SET_REPORTING_INTERVAL ACK_MOBILEAfter Defined Non-Zero Interval:

PUT_LOCATION11.4 Host Request Battery Level

Host-to-mobile Mobile-to-host GET_BATTERY_LEVEL PUT_BATTERY_LEVEL11.5 Host Request Radio Status

Host-to-mobile Mobile-to-host GET_RSSI PUT_RSSI11.6 Host Request GPS Status

Host-to-mobile Mobile-to-host GET_GPS_STATUS PUT_GPS_STATUS11.7 Host Set GPS Power State

Host-to-mobile Mobile-to-host SET_GPS_POWERSTATE ACK_MOBILE11.8 Host Set Buffering Interval

Host-to-mobile Mobile-to-host SET_BUFFERING_INTERVAL ACK_MOBILE11.9 Start Buffered Data Transmission

Host-to-mobile Mobile-to-host SET_START_BUFFER PUT_LOCATION

Repeats until a stop buffer transmission request is received or thenewest record has been transmitted:

PUT_LOCATION11.10 Stop Buffered Data Transmission

Host-to-mobile Mobile-to-host END_BUFFERED_DATA ACK_MOBILE11.11 Establish Circular Geofence

Host-to-mobile Mobile-to-host GET_GEOFENCE_HANDLE PUT_GEOFENCE_HANDLESET_CIRCULAR_GEOFENCE ACK_MOBILE11.12 Establish Polygon Geofence

Host-to-mobile Mobile-to-host GET_GEOFENCE_HANDLE PUT_GEOFENCE_HANDLESET_POLYGON_GEOFENCE ACK_MOBILE11.13 Establish Velocity Geofence

Host-to-mobile Mobile-to-host GET_GEOFENCE_HANDLE PUT_GEOFENCE_HANDLESET_VELOCITY_GEOFENCE ACK_MOBILE11.14 Establish Stationary Geofence

Host-to-mobile Mobile-to-host GET_GEOFENCE_HANDLE PUT_GEOFENCE_HANDLESET_STATIONARY_GEOFENCE ACK_MOBILE12. Reverse HTTP Transport Use Cases

Reverse HTTP Application-layer transactions are coupled with the HTTPtransport-layer transaction for mobile-initiated requests and decoupledfrom the HTTP transport-layer transaction for host-initiated requests.

12.1 Mobile Client First-Time Initialization or Cold-Start

Host-to-mobile Mobile-to-host GET_DEVICE_ID PUT_DEVICE_ID12.2 Idle State: Mobile Waiting for Command from Host

Mobile-to-host Host-to-mobile ACK_MOBILE ACK_HOST

In Reverse HTTP High Interactivity mode, a new HTTP session isestablished immediately. In Reverse HTTP Low Interactivity Mode, adefined interval elapses before the mobile re-polls the host for acommand. If any mobile-initiated events occur during this period, themobile established an HTTP session immediately and sends the host astructure.

ACK_MOBILE ACK_HOST or <any valid request>12.3 Host Request Location

Mobile-to-host Host-to-mobile ACK_MOBILE GET_CURRENT_LOCATIONPUT_CURRENT_LOCATION <any valid request>12.4 Start or Stop Interval Location Reporting

Mobile-to-host Host-to-mobile ACK_MOBILE SET_REPORTING_INTERVALACK_MOBILE <any valid request>

After defined non-zero interval:

PUT_LOCATION <any valid request>12.5 Host Request Battery Level

Mobile-to-host Host-to-mobile ACK_MOBILE GET_BATTERY_LEVELPUT_BATTERY_LEVEL <any valid request>12.6 Host Request Radio Status

Mobile-to-host Host-to-mobile ACK_MOBILE GET_RSSI PUT_RSSI <any validrequest>12.7 Host Request GPS Status

Mobile-to-host Host-to-mobile ACK_MOBILE GET_GPS_STATUS PUT_GPS_STATUS<any valid request>12.8 Host Set GPS Power State

Mobile-to-host Host-to-mobile ACK_MOBILE SET_GPS_POWERSTATE ACK_MOBILE<any valid request>12.9 Host Set Buffering Interval

Mobile-to-host Host-to-mobile ACK_MOBILE SET_BUFFERING_INTERVALACK_MOBILE <any valid request>12.10 Start Buffered Data Transmission

Mobile-to-host Host-to-mobile ACK_MOBILE GET_BUFFER PUT_LOCATION <anyvalid request>

After defined non-zero interval:

PUT_LOCATION <any valid request>12.11 End Buffered Data Transmission

Mobile-to-host Host-to-mobile ACK_MOBILE END_BUFFERED_DATA ACK_MOBILE<any valid request>12.12 Set Heartbeat Interval

Mobile-to-host Host-to-mobile ACK_MOBILE SET_HEARTBEAT_INTERVALACK_MOBILE <any valid request>12.13 Set Interactivity Mode

Mobile-to-host Host-to-mobile ACK_MOBILE SET_INTERACTIVITY_MODEACK_MOBILE <any valid request>

FIG. 5 is a flow chart summarizing a method 500 for communicating with atracking device using, for example, the above-described communicationprotocol. In a first step 502, communication is established between thetracking device (e.g., tracking device 102) and a remote system (e.g.,system 104) via a wireless network (e.g., a mobile phone network). Then,in a second step 504 configuration data is provided to the trackingdevice from the remote server. Next, in a third step 506, the remoteserver receives processed data from the tracking device. Then, in afourth step 508 a determination is made whether the configuration of thetracking device should be changed. If so, then in a fifth step 510,different configuration data is provided to the tracking device toreconfigure the tracking device. Then, in a sixth step 512, the remotesystem receives additional processed data from the tracking device,which has been processed and/or provided by the tracking device in thetracking device's new configuration. If in fourth step 508 it isdetermined that no configuration change is necessary, then method 500proceeds to sixth step 512 where the remote system receives additionprocessed data from the tracking device, but the additional processeddata will have been processed and/or provided by the tracking device inthe tracking device's first configuration.

The description of particular example embodiments of the presentinvention is now complete. Many of the described features may besubstituted, altered or omitted without departing from the scope of theinvention. For example, the tracking devices of the present inventioncan be embodied in an article of clothing worn by a tracked subject. Asanother example, tracking devices 102 and/or subscriber systems 118 canbe embodied in GPS enabled mobile telephones or other hand-held positiondetermining devices. These and other deviations from the particularembodiments shown will be apparent to those skilled in the art,particularly in view of the foregoing disclosure.

We claim:
 1. A tracking device comprising: a location detector operativeto determine locations of said tracking device; a communication deviceoperative to communicate with a remote system; memory for storing dataand code, said data including location data determined by said locationdetector and configuration data; a processor operative to execute saidcode to impart functionality to said tracking device, said functionalityof said tracking device depending at least in part on said configurationdata; a configuration routine operative to modify said configurationdata responsive to a communication from said remote system; and areporting routine operative to communicate operational data between saidtracking device and said remote system; and wherein said configurationdata modifiable responsive to said communication from said remote systemat least partially determines a power state of said location detector,said power state affecting the power usage of said location detector. 2.The tracking device of claim 1, wherein said configuration datamodifiable responsive to said communication from said remote system atleast partially determines an interval for communicating diagnosticinformation from said tracking device to said remote system.
 3. Thetracking device of claim 1, wherein said reporting routine is operativeto communicate said operational data to said remote system responsive toa request from said remote system.
 4. The tracking device of claim 1,wherein said operational data is indicative of a battery status.
 5. Thetracking device of claim 1, wherein said operational data is indicativeof a radio signal strength.
 6. The tracking device of claim 1, whereinsaid operational data is indicative of a status of said locationdetector.
 7. The tracking device of claim 6, wherein said operationaldata is indicative of a fix state of said location detector.
 8. Thetracking device of claim 6, wherein said operational data is indicativeof a power state of said location detector.
 9. The tracking device ofclaim 1, wherein said reporting routine, responsive to a request fromsaid remote system, is operative to communicate diagnostic data to saidremote system.
 10. A method for communicating with a tracking device,said method comprising: communicating with said tracking device via awireless network; providing configuration data to said tracking devicevia said wireless network, said configuration data causing said trackingdevice to operate according to a first configuration; receivingprocessed data from said tracking device, said processed data beinggenerated by said tracking device in said first configuration; andproviding new configuration data to said tracking device via saidwireless network, said new configuration data based at least in part onsaid processed data and changing said first configuration of saidtracking device to a different configuration; and wherein saidconfiguration data at least partially determines a power state of saidtracking device, said power state affecting the power usage of saidtracking device.
 11. The method of claim 10, wherein said configurationdata at least partially determines a diagnostic reporting interval. 12.The method of claim 10, wherein said processed data includes dataindicative of a battery status of said tracking device.
 13. The methodof claim 10, wherein said processed data includes data indicative of aradio signal strength determined by said tracking device.
 14. The methodof claim 10, wherein said processed data includes data generated by adiagnostic routine of said tracking device.
 15. The method of claim 10,wherein: said first configuration is associated with a first trackingfunction; and said different configuration is associated with adifferent tracking function.
 16. The method of claim 10, furthercomprising requesting said processed data from said tracking device. 17.A tracking device comprising: a location detector operative to determinelocations of said tracking device; a communication device operative tocommunicate with a remote system; memory for storing data and code, saiddata including location data determined by said location detector andconfiguration data; a processor operative to execute said code to impartfunctionality to said tracking device, said functionality of saidtracking device depending at least in part on said configuration data; aconfiguration routine operative to modify said configuration dataresponsive to a communication from said remote system; and a reportingroutine operative to communicate operational data between said trackingdevice and said remote system; and wherein said configuration datamodifiable responsive to said communication from said remote system atleast partially determines an interval for communicating diagnosticinformation from said tracking device to said remote system.
 18. Thetracking device of claim 17, wherein said reporting routine is operativeto communicate said operational data to said remote system responsive toa request from said remote system.
 19. The tracking device of claim 17,wherein said operational data is indicative of a battery status.
 20. Thetracking device of claim 17, wherein said operational data is indicativeof a radio signal strength.
 21. The tracking device of claim 17, whereinsaid operational data is indicative of a status of said locationdetector.
 22. The tracking device of claim 21, wherein said operationaldata is indicative of a fix state of said location detector.
 23. Thetracking device of claim 21, wherein said operational data is indicativeof a power state of said location detector.
 24. The tracking device ofclaim 17, wherein said reporting routine, responsive to a request fromsaid remote system, is operative to communicate diagnostic data to saidremote system.
 25. A method for communicating with a tracking device,said method comprising: communicating with said tracking device via awireless network; providing configuration data to said tracking devicevia said wireless network, said configuration data causing said trackingdevice to operate according to a first configuration; receivingprocessed data from said tracking device, said processed data beinggenerated by said tracking device in said first configuration; andproviding new configuration data to said tracking device via saidwireless network, said new configuration data based at least in part onsaid processed data and changing said first configuration of saidtracking device to a different configuration; and wherein saidconfiguration data at least partially determines a diagnostic reportinginterval.
 26. The method of claim 25, wherein said processed dataincludes data indicative of a battery status of said tracking device.27. The method of claim 25, wherein said processed data includes dataindicative of a radio signal strength determined by said trackingdevice.
 28. The method of claim 25, wherein said processed data includesdata generated by a diagnostic routine of said tracking device.
 29. Themethod of claim 25, wherein: said first configuration is associated witha first tracking function; and said different configuration isassociated with a different tracking function.
 30. The method of claim25, further comprising requesting said processed data from said trackingdevice.
 31. A tracking device comprising: a location detector operativeto determine locations of said tracking device; a communication deviceoperative to communicate with a remote system; memory for storing dataand code, said data including location data determined by said locationdetector and configuration data; a processor operative to execute saidcode to impart functionality to said tracking device, said functionalityof said tracking device depending at least in part on said configurationdata; a configuration routine operative to modify said configurationdata responsive to a communication from said remote system; and areporting routine operative to communicate operational data between saidtracking device and said remote system; and wherein said operationaldata is indicative of a battery status.
 32. The tracking device of claim31, wherein said reporting routine is operative to communicate saidoperational data to said remote system responsive to a request from saidremote system.
 33. The tracking device of claim 31, wherein saidoperational data is indicative of a radio signal strength.
 34. Thetracking device of claim 31, wherein said operational data is indicativeof a status of said location detector.
 35. The tracking device of claim34, wherein said operational data is indicative of a fix state of saidlocation detector.
 36. The tracking device of claim 34, wherein saidoperational data is indicative of a power state of said locationdetector.
 37. The tracking device of claim 31, wherein said reportingroutine, responsive to a request from said remote system, is operativeto communicate diagnostic data to said remote system.
 38. A method forcommunicating with a tracking device, said method comprising:communicating with said tracking device via a wireless network;providing configuration data to said tracking device via said wirelessnetwork, said configuration data causing said tracking device to operateaccording to a first configuration; receiving processed data from saidtracking device, said processed data being generated by said trackingdevice in said first configuration; and providing new configuration datato said tracking device via said wireless network, said newconfiguration data based at least in part on said processed data andchanging said first configuration of said tracking device to a differentconfiguration; and wherein said processed data includes data indicativeof a battery status of said tracking device.
 39. The method of claim 38,wherein said processed data includes data indicative of a radio signalstrength determined by said tracking device.
 40. The method of claim 38,wherein said processed data includes data generated by a diagnosticroutine of said tracking device.
 41. The method of claim 38, wherein:said first configuration is associated with a first tracking function;and said different configuration is associated with a different trackingfunction.
 42. The method of claim 38, further comprising requesting saidprocessed data from said tracking device.
 43. A tracking devicecomprising: a location detector operative to determine locations of saidtracking device; a communication device operative to communicate with aremote system; memory for storing data and code, said data includinglocation data determined by said location detector and configurationdata; a processor operative to execute said code to impart functionalityto said tracking device, said functionality of said tracking devicedepending at least in part on said configuration data; a configurationroutine operative to modify said configuration data responsive to acommunication from said remote system; and a reporting routine operativeto communicate operational data between said tracking device and saidremote system; and wherein said operational data is indicative of astatus of said location detector; and said operational data isindicative of a fix state of said location detector.
 44. The trackingdevice of claim 43, wherein said reporting routine is operative tocommunicate said operational data to said remote system responsive to arequest from said remote system.
 45. The tracking device of claim 43,wherein said operational data is indicative of a radio signal strength.46. The tracking device of claim 43, wherein said operational data isindicative of a power state of said location detector.
 47. The trackingdevice of claim 43, wherein said reporting routine, responsive to arequest from said remote system, is operative to communicate diagnosticdata to said remote system.
 48. A method for communicating with atracking device, said method comprising: communicating with saidtracking device via a wireless network; providing configuration data tosaid tracking device via said wireless network, said configuration datacausing said tracking device to operate according to a firstconfiguration; receiving processed data from said tracking device, saidprocessed data being generated by said tracking device in said firstconfiguration; and providing new configuration data to said trackingdevice via said wireless network, said new configuration data based atleast in part on said processed data and changing said firstconfiguration of said tracking device to a different configuration; andwherein said first configuration is associated with a first trackingfunction; and said different configuration is associated with adifferent tracking function.
 49. The method of claim 48, wherein saidprocessed data includes data indicative of a radio signal strengthdetermined by said tracking device.
 50. The method of claim 48, whereinsaid processed data includes data generated by a diagnostic routine ofsaid tracking device.
 51. The method of claim 48, further comprisingrequesting said processed data from said tracking device.